Electronic devices for capturing media content and transmitting the media content to a network accessible media repository and methods of operating the same

ABSTRACT

A client device is operated by providing a media content record function, receiving a user invocation of the media content record function, recording media content responsive to the user invocation of the media content record function, obtaining a list of authorized recipients for the media content, receiving a user selection of at least one of the authorized recipients for the media content, associating the selected at least one of the authorized recipients with the media content, and transmitting the media content along with information identifying the at least one of the authorized recipients associated therewith from the client device to a network accessible media repository for storage therein. The media content includes audio, video, and/or image content.

BACKGROUND OF THE INVENTION

The present invention relates to managing media content, and, moreparticularly, to methods, systems, and computer program products formanaging media content in a communication network.

Various electronic devices, such as Personal Digital Assistants (PDAs),have been developed to help people manage their affairs. PDAs wereoriginally designed to function primarily as personal organizers, buthave evolved to be used in a variety of ways, such as a calculator, aclock, a calendar, a game, an Internet access device, an electronic maildevice, a radio, an audio recorder, a video recorder, a camera, anaddress book, a phone, and/or a spreadsheet. Some such devices may beused by people to create audio memos to assist in managing tasks forthemselves, their family, and/or friends. “Memory jogger” solutions havetraditionally been designed for a single user. For example, devices withpersonal recorders or dictation functions may be used to record audiomemos, but generally require the original device to retrieve the memo.Voice messaging systems may allow a caller to leave a message for missedcalled parties. A voice message must typically be delivered separatelyto each called party and the voice messages are generally managed by thereceiver, not the sender. Moreover, voice messages are typicallyassociated with the called party phone number, not an individual.

SUMMARY

According to some embodiments of the present invention, a client deviceis operated by providing a media content record function, receiving auser invocation of the media content record function, recording mediacontent responsive to the user invocation of the media content recordfunction, obtaining a list of authorized recipients for the mediacontent, receiving a user selection of at least one of the authorizedrecipients for the media content, associating the selected at least oneof the authorized recipients with the media content, and transmittingthe media content along with information identifying the at least one ofthe authorized recipients associated therewith from the client device toa network accessible media repository for storage therein. The mediacontent comprises audio, video, and/or image content.

In other embodiments, recording the media content, receiving a userselection of the at least one of the authorized recipients, associatingthe selected at least one of the authorized recipients, and transmittingthe media content are performed responsive to at least one promptprovided via the client device.

In other embodiments, the at least one prompt is a visual prompt.

In still other embodiments, the at least one prompt is an audibleprompt.

In still other embodiments, recording the media content comprisesrecording the media content while maintaining a call session at theclient device.

In still other embodiments, the client device comprises a soft recordkey, and receiving a user invocation of the media content recordfunction comprises receiving a user invocation of the soft record key.

In still other embodiments, the client device comprises a hard recordkey, and receiving a user invocation of the media content recordfunction comprises receiving a user invocation of the hard record key.

In still other embodiments, the media content is audio content.

In still other embodiments, the client device is an Internet Protocol(IP) device.

In further embodiments, a client device comprises a media content recordfunction that is configured to record media content, and a processorthat is communicatively coupled to the media content record function andis configured to obtain a list of authorized recipients for the mediacontent, associate at least one of the authorized recipients with themedia content, and transmit the media content along with informationidentifying that at least one of the authorized recipients associatedtherewith from the client device to a network accessible mediarepository for storage therein. The media content comprises audio,video, and/or image content.

In still further embodiments, the processor is configured to provide atleast one prompt to a user of the client device and to receive a userselection of the at least one of the authorized recipients responsive tothe at least one prompt.

In still further embodiments, the processor is configured to associatethe at least one of the authorized recipients with the media content andto transmit the media content along with information identifying that atleast one of the authorized recipients associated therewith from theclient device to the network accessible media repository responsive tothe at least one prompt.

In still further embodiments, the client device further comprises adisplay that is communicatively coupled to the processor and the atleast one prompt is a visual prompt on the display.

In still further embodiments, the client device further comprises aspeaker that is communicatively coupled to the processor and the atleast one prompt is an audible prompt played through the speaker.

In still further embodiments, the media content record function isconfigured to record the media content while the client device maintainsa call session.

In still further embodiments, the client device further comprises a softrecord key that is communicatively coupled to the media content recordfunction, the media content record function being configured to recordthe media content responsive to user invocation of the soft record key.

In still further embodiments, the client device further comprises a hardrecord key that is communicatively coupled to the media content recordfunction, the media content record function being configured to recordthe media content responsive to user invocation of the hard record key.

In still further embodiments, the media content is audio content.

In still further embodiments, the client device is an Internet Protocol(IP) device.

Other systems, methods, and/or computer program products according toembodiments of the invention will be or become apparent to one withskill in the art upon review of the following drawings and detaileddescription. It is intended that all such additional systems, methods,and/or computer program products be included within this description, bewithin the scope of the present invention, and be protected by theaccompanying claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Other features of the present invention will be more readily understoodfrom the following detailed description of specific embodiments thereofwhen read in conjunction with the accompanying drawings, in which:

FIG. 1 is a block diagram that illustrates a communication networkarchitecture for managing media content in accordance with someembodiments of the present invention;

FIG. 2 is a block diagram of a data processing system that can be usedto implement media servers shown in FIG. 1;

FIG. 3 is a block diagram that illustrates a software/hardwarearchitecture for a media storage server in accordance with someembodiments of the present invention;

FIG. 4 is a block diagram that illustrates a software/hardwarearchitecture for a media retrieval server in accordance with someembodiments of the present invention;

FIG. 5 is a block diagram of a client device in accordance with someembodiments of the present invention; and

FIGS. 6-8 are flowcharts that illustrate operations for managing mediacontent in accordance with some embodiments of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

While the invention is susceptible to various modifications andalternative forms, specific embodiments thereof are shown by way ofexample in the drawings and will herein be described in detail. Itshould be understood, however, that there is no intent to limit theinvention to the particular forms disclosed, but on the contrary, theinvention is to cover all modifications, equivalents, and alternativesfalling within the spirit and scope of the invention as defined by theclaims. Like reference numbers signify like elements throughout thedescription of the figures.

As used herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless expressly stated otherwise. Itshould be further understood that the terms “comprises” and/or“comprising” when used in this specification is taken to specify thepresence of stated features, integers, steps, operations, elements,and/or components, but does not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof. It will be understood that when anelement is referred to as being “connected” or “coupled” to anotherelement, it can be directly connected or coupled to the other element orintervening elements may be present. Furthermore, “connected” or“coupled” as used herein may include wirelessly connected or coupled. Asused herein, the term “and/or” includes any and all combinations of oneor more of the associated listed items.

Unless otherwise defined, all terms (including technical and scientificterms) used herein have the same meaning as commonly understood by oneof ordinary skill in the art to which this invention belongs. It will befurther understood that terms, such as those defined in commonly useddictionaries, should be interpreted as having a meaning that isconsistent with their meaning in the context of the relevant art andwill not be interpreted in an idealized or overly formal sense unlessexpressly so defined herein.

The present invention may be embodied as methods, systems, and/orcomputer program products. Accordingly, the present invention may beembodied in hardware and/or in software (including firmware, residentsoftware, micro-code, etc.). Furthermore, the present invention may takethe form of a computer program product on a computer-usable orcomputer-readable storage medium having computer-usable orcomputer-readable program code embodied in the medium for use by or inconnection with an instruction execution system. In the context of thisdocument, a computer-usable or computer-readable medium may be anymedium that can contain, store, communicate, propagate, or transport theprogram for use by or in connection with the instruction executionsystem, apparatus, or device.

The computer-usable or computer-readable medium may be, for example butnot limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, device, or propagationmedium. More specific examples (a nonexhaustive list) of thecomputer-readable medium would include the following: an electricalconnection having one or more wires, a portable computer diskette, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,and a compact disc read-only memory (CD-ROM). Note that thecomputer-usable or computer-readable medium could even be paper oranother suitable medium upon which the program is printed, as theprogram can be electronically captured, via, for instance, opticalscanning of the paper or other medium, then compiled, interpreted, orotherwise processed in a suitable manner, if necessary, and then storedin a computer memory.

As used herein, the term “Internet Protocol (IP) terminal or device”refers to a terminal or device that may communicate using the sessioninitiation protocol (SIP). It will be understood that an IP terminal ordevice may also refer to devices that communicate using SIP via a mediagateway, which translates communications, for example, between an IPnetwork and another network, such as the public switched telephonenetwork or a circuit switched wireless network.

Some embodiments of the present invention are described herein withrespect to managing audio files or messages. It will be understood thatthe present invention is not limited to these examples as the principlesof the present invention can be applied to media content generally,including, but not limited to, video files, image/picture files, textfiles, and/or data files.

Some embodiments of the present invention arise from a realization thatmedia content can be captured or recorded at a client device and thentransmitted to a network accessible media storage repository where itcan be retrieved by others who have been authorized to access the mediacontent. Advantageously, messages or memos, for example, can berelatively easily distributed to an audience of people without the needto repeat the messages or memos for each individual recipient. The memosor messages can be retrieved using various types of devices and does notrequire the use of any specific device, such as the client device thatoriginally captured or recorded the memo or message.

Referring now to FIG. 1, an exemplary communication network 100, inaccordance with some embodiments of the present invention, comprises anInternet Protocol (IP) multimedia subsystem (IMS) network 105 that iscoupled to a packet switching network 110 and a Public SwitchedTelephone Network (PSTN)/Public Land Mobile Network (PLMN) 115. Thepacket switching network 110 is coupled to a WiFi access network 120.The PSTN/PLMN network 115 is coupled to a mobile switching center 125,which supports, for example, a Global System for Mobile Communications(GSM)/Universal Mobile Telecommunications System (UMTS) access network130. It will be understood that embodiments of the present invention arenot limited to GSM and/or UMTS. Other cellular communication protocolscan be used, such as, for example, Advanced Mobile Phone Service (AMPS),ANSI-136, General Packet Radio Service (GPRS), enhanced data rates forGSM evolution (EDGE), code division multiple access (CDMA),wideband-CDMA, and/or CDMA2000. As shown in FIG. 1, cellular basestations comprising the access network 130 may be connected to one ormore mobile switching centers 125, which, in turn, can be connected to aPSTN/PLMN 115 or other network.

The packet switching network 110 and the PSTN/PLMN may provide eitherdirect or indirect network access to various types of client devices.For example, the packet switching network 110 via the WiFi accessnetwork 120 may provide network access to a WiFi client device 135 a.The packet switching network 110 may also provide network accessdirectly to a client device 135 b. The PSTN/PLMN 115 may provide networkaccess to a GSM client device 135 c indirectly through the GSM/UMTSaccess network 130 and the mobile switching center 125. The PSTN/PLMN115 may also provide network access directly to a conventional Plain OldTelephone Service (POTS) phone 135 d. The client devices 135 a, 135 b,and 135 c may be IP client devices in that they may be capable ofcommunicating using SIP. Client device 135 d may not be capable ofsetting up communication sessions via SIP.

The packet switching network 110 connects to the IMS network 105 via thenetwork control platform 140. The network control platform 140 comprisesa call session control function (CSCF) 145. The CSCF 145 is connected toa media storage server 165 and a media retrieval server 175 and enablesthe registration of IP terminals/devices and the routing of SIPsignaling messages between the servers 165 and 175 and the clientdevices 135 a and 135 b. The CSCF 145 may provide similar functionalityfor the client devices 135 c and 135 d connected to the network 105 viaa media gateway 150 and a media gateway control function (MGCF) 155. TheMGCF 155 enables SIP signaling to inter-work with other types ofsignaling used by the media gateway 150. Thus, the combination of theMGCF 155 and the media gateway 150 may provide an interface between theSIP signaling used in the IMS network 105 and the signaling used in thePSTN/PLMN 115.

The IMS network 105 may further comprise a home subscriber server (HSS)database 160 that maintains a service profile and other information foreach end-user and associated IP terminal/device that has registered withthe IMS network 105. The profile and other information may include, butis not limited to, IP address information, roaming information, and/ortelephony services information.

The media storage server 165 may be configured to facilitate the storageof media content that has been recorded or captured on a client deviceand transmitted to the media storage server 165. In more detail, themedia storage server 165 may store the media content in a mediarepository 170. In some embodiments, the media content may be stored ina database in the media repository 170. It will be appreciated that amedia content database may be implemented using any of a number ofdifferent types of database structures, including, but not limited to,databases following relational, hierarchical, network and objectdatabase models. Generally, a media repository may be implemented in asingle storage device or distributed over multiple devices in, forexample, a networked configuration.

The media retrieval server 175 may be configured to allow client devicesto access media content that has been stored on the media repository170. In some embodiments, the media retrieval server 175 may communicatewith a security information repository 180 that contains informationidentifying who is authorized to access the various media content filesthat have been stored in the media repository 170. The securityinformation may be stored in a database in the security informationrepository 180. Like the media content database, the securityinformation database may be implemented using any of a number ofdifferent types of database structures, including, but not limited to,databases following relational, hierarchical, network and objectdatabase models. The security information repository may be implementedin a single storage device or distributed over multiple devices in, forexample, a networked configuration.

Although shown as separate servers, the media storage server 165 and themedia retrieval server 175 may be implemented as a single server,separate servers, or a network of servers either co-located in a serverfarm, for example, or located in different geographic locations.Likewise, the media repository 170 and the security informationrepository 180 may be implemented as a single repository, separaterepositories, or a network of repositories located in a single locationor in different geographic locations.

The various elements of the communication network 100 may be connectedby a global network, such as the Internet or other publicly accessiblenetwork. Various elements of the network may be interconnected by a widearea network, a local area network, an Intranet, and/or other privatenetwork, which may not accessible by the general public. Thus, thecommunication network 100 may represent a combination of public andprivate networks or a virtual private network (VPN). Although FIG. 1illustrates an exemplary communication network, it will be understoodthat the present invention is not limited to such configurations, but isintended to encompass any configuration capable of carrying out theoperations described herein.

Referring now to FIG. 2, a data processing system 200 that may be usedto implement the media storage server 165 and/or the media retrievalserver 175 of FIG. 1, in accordance with some embodiments of the presentinvention, comprises input device(s) 202, such as a keyboard or keypad,a display 204, and a memory 206 that communicate with a processor 208.The data processing system 200 may further include a storage system 210,a speaker 212, and an input/output (I/O) data port(s) 214 that alsocommunicate with the processor 208. The storage system 210 may includeremovable and/or fixed media, such as floppy disks, ZIP drives, harddisks, or the like, as well as virtual storage, such as a RAMDISK. TheI/O data port(s) 214 may be used to transfer information between thedata processing system 200 and another computer system or a network(e.g., the Internet). These components may be conventional components,such as those used in many conventional computing devices, and theirfunctionality, with respect to conventional operations, is generallyknown to those skilled in the art. The memory 206 may be configured witha database manager 216 that may be used to manage the securityinformation in the security information repository 180 and/or the mediacontent in the media repository 170.

FIG. 3 illustrates a processor 300 and memory 305 that may be used inembodiments of the media storage server 165 of FIG. 1 and dataprocessing system 200 of FIG. 2 in accordance with some embodiments ofthe present invention. The processor 300 communicates with the memory305 via an address/data bus 310. The processor 300 may be, for example,a commercially available or custom microprocessor. The memory 305 isrepresentative of the one or more memory devices containing the softwareand data used for managing media content in a media repository, such asthe media repository 170 of FIG. 1, in accordance with some embodimentsof the present invention. The memory 305 may include, but is not limitedto, the following types of devices: cache, ROM, PROM, EPROM, EEPROM,flash, SRAM, and DRAM.

As shown in FIG. 3, the memory 305 may contain up to two or morecategories of software and/or data: an operating system 315 and a mediastorage manager 320. The operating system 315 generally controls theoperation of the media storage server. In particular, the operatingsystem 315 may manage the media storage server's software and/orhardware resources and may coordinate execution of programs by theprocessor 300. The media storage manager 320 may be configured toreceive media content that is recorded/captured at a client device andtransmitted thereto and confirm that the sender is authorized to storethe media content in the media repository. The media storage manager 320may also be configured to interface with a database that is used tostore and provide access to the media content in the media repository.

FIG. 4 illustrates a processor 400 and memory 405 that may be used inembodiments of the media retrieval server 175 of FIG. 1 and dataprocessing system 200 of FIG. 2 in accordance with some embodiments ofthe present invention. The processor 400 communicates with the memory405 via an address/data bus 410. The processor 400 may be, for example,a commercially available or custom microprocessor. The memory 405 isrepresentative of the one or more memory devices containing the softwareand data used for controlling access to media content that is stored inthe media repository 170 of FIG. 1, in accordance with some embodimentsof the present invention. The memory 405 may include, but is not limitedto, the following types of devices: cache, ROM, PROM, EPROM, EEPROM,flash, SRAM, and DRAM.

As shown in FIG. 4, the memory 405 may contain up to three or morecategories of software and/or data: an operating system 415, a mediaretrieval manager 420, and a security manager 425. The operating system415 generally controls the operation of the media retrieval server. Inparticular, the operating system 415 may manage the media retrievalserver's software and/or hardware resources and may coordinate executionof programs by the processor 400. The media retrieval manager 420 may beconfigured to interface with the media repository and, in someembodiments, the database that is used to store the media content in themedia repository so as to be able to retrieve a requested media contentfile and provide access to the requested media content to a requestinguser/client device. In some embodiments, the media retrieval manager 420may play the media content back through the network to the requestingclient device. In other embodiments, the media retrieval manager 420 maydownload the media content to the requesting client device. The securitymanager 425 may be configured to maintain lists of authorized recipientsfor media content files in the security information repository 180 thatmay be downloaded to a client device to allow the user of the clientdevice to determine who will be allowed to access a media content filethat is to be stored in the media repository. The security manager 425may also authenticate/authorize users and/or client devices whenrequests are made to access media content stored in the mediarepository.

Although FIGS. 3 and 4 illustrate exemplary hardware/softwarearchitectures that may be used in media storage servers and mediaretrieval servers, respectively, such as the media storage server 165and media retrieval server 175 of FIG. 1, it will be understood that thepresent invention is not limited to such a configuration but is intendedto encompass any configuration capable of carrying out operationsdescribed herein. Moreover, the functionality of the data processingsystem 200 of FIG. 2 and the hardware/software architectures of FIGS. 3and 4 may be implemented as a single processor system, a multi-processorsystem, or even a network of stand-alone computer systems, in accordancewith various embodiments of the present invention.

Computer program code for carrying out operations of data processingsystems discussed above with respect to FIG. 2 and/or the softwaremodules discussed above with respect to FIGS. 3 and 4 may be written ina high-level programming language, such as Java, C, and/or C++, fordevelopment convenience. In addition, computer program code for carryingout operations of embodiments of the present invention may also bewritten in other programming languages, such as, but not limited to,interpreted languages. Some modules or routines may be written inassembly language or even micro-code to enhance performance and/ormemory usage. It will be further appreciated that the functionality ofany or all of the program modules may also be implemented using discretehardware components, one or more application specific integratedcircuits (ASICs), or a programmed digital signal processor ormicrocontroller.

Referring now to FIG. 5, an exemplary client device/mobile terminal 500,in accordance with some embodiments of the present invention, mayinclude, but is not limited to, a microphone 505, a speaker 510, akeyboard/keypad 515, a display 520, a transceiver 525, a record function555, and a memory 565 that communicate with a processor 535. Themicrophone 505 may represent a single microphone or may representmultiple microphones. The transceiver 525 includes a transmitter circuit540 and a receiver circuit 545, which, respectively, transmit outgoingradio frequency signals to, for example, base station transceivers andreceive incoming radio frequency signals from, for example, the basestation transceivers via an antenna 550. The radio frequency signalstransmitted between the client device 500 and the base stationtransceivers may comprise both traffic and control signals (e.g., pagingsignals/messages for incoming calls), which are used to establish andmaintain communication with another party or destination. The radiofrequency signals may also comprise packet data information, such as,for example, cellular digital packet data (CDPD) information. Theforegoing components of the client device 500, without the capabilitiesof the present invention, may be included in many conventional clientdevices and their functionality, with respect to such conventionaloperations, is generally known to those skilled in the art.

As shown in FIG. 5, the client device 500 includes a record function 555that may be used to record media content, such as audio content, via themicrophone 505. Advantageously, the record function 555 may be used torecord media content at the client device 500 while simultaneouslymaintaining an active call session at the client device 500. Inaccordance with various embodiments of the present invention, the clientdevice 500 may be configured with a hard record key 560 as part of thestructure of the client device 500 that can be invoked by a user torecord media content. In other embodiments, the memory 565 may beconfigured with a soft record key module 570 that provides a menu optionon the display 520 that a user may select or invoke using thekeyboard/keypad 515 to record media content. To assist a user inrecording or capturing media content and transmitting the media contentto a media repository, such as the media repository 170 of FIG. 1, theclient device 500 may further include a memo user interface module 575in the memory 565 that may be configured to provide the user with visualand/or audible prompts via the display 520 and/or speaker 510.

The present invention is described hereinafter with reference toflowchart and/or block diagram illustrations of methods, systems, clientdevices, and/or computer program products in accordance with someembodiments of the invention. These flowchart and/or block diagramsfurther illustrate exemplary operations of recording or capturing mediacontent and storing the media content in a media repository inaccordance with various embodiments of the present invention. It will beunderstood that each block of the flowchart and/or block diagramillustrations, and combinations of blocks in the flowchart and/or blockdiagram illustrations, may be implemented by computer programinstructions and/or hardware operations. These computer programinstructions may be provided to a processor of a general purposecomputer, a special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor of the computer or other programmabledata processing apparatus, create means for implementing the functionsspecified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerusable or computer-readable memory that may direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer usable orcomputer-readable memory produce an article of manufacture includinginstructions that implement the function specified in the flowchartand/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions that execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart and/or block diagram block or blocks.

Operations for managing media content, in accordance with someembodiments of the present invention, will now be described withreference to the flowcharts of FIGS. 6-8 and the communication networkarchitecture of FIG. 1. Referring now to FIG. 6, operations begin atblock 600 where a client device 135 may cooperate with the mediaretrieval server 175 to define a list of authorized recipients that auser of the client device 135 may wish to allow to access media contentfiles that are stored in the media repository 175 by the user. In someembodiments, a user may upload his/her contacts from the client deviceto the media retrieval server 175. In other embodiments, the mediaretrieval server 175 may provide an interface that allows users todefine recipients and/or client devices that are authorized to accessthe stored media content. By storing the list of authorized recipientsat a network server, a user may maintain a common list for use withmultiple client devices in one location without the need to synchronizemultiple client devices with each other when a change is made to onedevice.

At block 605, the user may record media content at the client device135. As discussed above with respect to FIG. 5, the user may invoke arecord function on the client device 135 using a hard record key or asoft record key that is provided through the display of the clientdevice 135. Moreover, in some embodiments, the user can initiate a mediarecord operation while maintaining an active call session via the clientdevice 135. The media content may be an audio message, such as a memo,that is recorded via a microphone, in some embodiments of the presentinvention. It will be understood, however, that the media content is notlimited to audio files, but may be, but is not limited to, a picturecaptured via a camera, a video captured via a video recorder, a passageof text captured via a text editor or scanner, etc.

At block 610 the client device 135 may obtain the list of authorizedrecipients for accessing the stored media content that was defined atblock 600. The user may select one or more recipients to associate withthe recorded media content using, for example, a user interface on thedisplay of the client device 135 at block 615. The recorded mediacontent along with the identities of one or more authorized recipientsare then transmitted from the client device 135 to the media storageserver 165 for storage in the media repository 170 at block 620. Asdiscussed above with respect to FIG. 5, the memo user interface module575 may provide visual and/or audible prompts to assist a user inrecording media content, obtaining the list of authorized recipients,associating one or more recipients with the recorded media content, andtransmitting the media content to the media storage server 165.

Referring now to FIG. 7, operations for storing the recorded mediacontent in the media repository, in accordance with some embodiments ofthe present invention, begin at block 700 where the client device 135 isauthenticated. In accordance with some embodiments of the presentinvention, the client device 135 may be an IP device that isauthenticated in the IMS network 105. For example, referring to FIG. 1,the CSCF 145 may be configured to cooperate with various authenticationdatabases/systems, such as the HSS database 160, that maintain a serviceprofile and other information for each end-user and associated SIP/IMSterminal/device that has registered with the CSCF 145. The profile andother information may include, but is not limited to, IP addressinformation, roaming information, and/or telephony services information.The CSCF 145 may cooperate with at least one service control point(SCP), which manages a home location register (HLR) for the CSCF 145.The HLR is a database that contains information, such as registrationinformation, call settings, subscribed features, location information,directory information, identification information, and/or otherinformation concerning mobile terminals that are subscribed to the CSCF145. The HLR is also used to authenticate mobile terminals and tosupport mobility management features to which the user of a mobileterminal has subscribed when that user is roaming.

In other embodiments, the client device may be authenticated at themedia storage server 165. In some embodiments, the client device 135 maybe authenticated using the Secure Sockets Layer (SSL) protocol, which isa cryptographic protocol that provides secure communications on networksfor various applications, including data transfers.

Returning to FIG. 7, the media storage server 165 may determine at block710 whether the user and/or client device 135 is authorized to storemedia content on the media repository 170. In some embodiments, thisauthorization may be performed by verifying the authenticationinformation obtained via the IMS network 105. In other embodiments, auser may be required to submit a user identification and password toaccess the media storage service. Once the user and/or client device 135have been authenticated and authorized, the media content is stored inthe media repository 170 at block 720.

Referring now to FIG. 8, operations for retrieving media content via aclient device 135 that has previously been stored in the mediarepository 170 begin at block 800 where the media retrieval server 175receives a request from a client device 135 to access a stored mediacontent file. In accordance with various embodiments of the presentinvention, the user and/or requesting client device may be authenticatedthrough the IMS network 105 or at the media retrieval server 175 asdiscussed above with respect to block 700 of FIG. 7 and the mediastorage server 165. Moreover, the requesting client device 135 may, forexample, use SSL to securely communicate with the media retrieval server175 to access a stored media content file.

The media retrieval server 175 may determine at block 820 whether theuser and/or requesting client device 135 is authorized to store mediacontent on the media repository 170. In some embodiments, thisauthorization may be performed by verifying the authenticationinformation obtained via the IMS network 105. In other embodiments, auser may be required to submit a user identification and password toobtain access to a stored media content file. In some embodiments, themedia retrieval server 175 may determine that the authenticatedrequesting user and/or client device is authorized to access therequested media content by comparing the identity of a user associatedwith the requesting client device with the identities of the authorizedrecipients stored in the security information repository 180 that wereassociated with the media content before transmitting the media contentfor storage in the media repository 170 as discussed above with respectto block 615 of FIG. 6.

Once the user and/or requesting client device 135 have beenauthenticated and authorized, the requested media content is provided tothe requesting client device 135 at block 830. In some embodiments, therequested content may be played through the network to the requestingclient device. In other embodiments, the requesting client device 135may be allowed to download the requested media content through thenetwork.

Advantageously, the user and/or client device that was used tooriginally record the media content for storage in the media repositorymay be different from the requesting user and/or client device thatseeks access to the stored media content. In this way, messages, memos,pictures, text, and/or other media can be relatively easily distributedto an audience of people without the need to repeat the messages ormemos for each individual recipient. The memos or messages can beretrieved using various types of devices and does not require the use ofany specific device.

The flowcharts of FIGS. 6-8 illustrate the architecture, functionality,and operations of embodiments of methods, systems, and/or computerprogram products for managing media content. In this regard, each blockrepresents a module, segment, or portion of code, which comprises one ormore executable instructions for implementing the specified logicalfunction(s). It should also be noted that in other implementations, thefunction(s) noted in the blocks may occur out of the order noted inFIGS. 6-8. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently or the blocks may sometimes beexecuted in the reverse order, depending on the functionality involved.Many variations and modifications can be made to the embodiments withoutsubstantially departing from the principles of the present invention.All such variations and modifications are intended to be included hereinwithin the scope of the present invention, as set forth in the followingclaims.

1. A method of operating a client device, comprising: providing a mediacontent record function, the media content comprising audio, video,and/or image content; receiving a user invocation of the media contentrecord function; recording media content responsive to the userinvocation of the media content record function; obtaining a list ofauthorized recipients for the media content; receiving a user selectionof at least one of the authorized recipients for the media content;associating the selected at least one of the authorized recipients withthe media content; and transmitting the media content along withinformation identifying the at least one of the authorized recipientsassociated therewith from the client device to a network accessiblemedia repository for storage therein.
 2. The method of claim 1, whereinrecording the media content, receiving a user selection of the at leastone of the authorized recipients, associating the selected at least oneof the authorized recipients, and transmitting the media content areperformed responsive to at least one prompt provided via the clientdevice.
 3. The method of claim 2, wherein the at least one prompt is avisual prompt.
 4. The method of claim 2, wherein the at least one promptis an audible prompt.
 5. The method of claim 1, wherein recording themedia content comprises: recording the media content while maintaining acall session at the client device.
 6. The method of claim 1, wherein theclient device comprises a soft record key, and wherein receiving a userinvocation of the media content record function comprises receiving auser invocation of the soft record key.
 7. The method of claim 1,wherein the client device comprises a hard record key, and whereinreceiving a user invocation of the media content record functioncomprises receiving a user invocation of the hard record key.
 8. Themethod of claim 1, wherein the media content is audio content.
 9. Themethod of claim 1, wherein the client device is an Internet Protocol(IP) device.
 10. A computer program product comprising computer-readableprogram code embodied on a computer-readable medium, the computerreadable program code being configured to carry out the method ofclaim
 1. 11. A client device, comprising: a media content recordfunction that is configured to record media content, the media contentcomprising audio, video, and/or image content; and a processor that iscommunicatively coupled to the media content record function and isconfigured to obtain a list of authorized recipients for the mediacontent, associate at least one of the authorized recipients with themedia content, and transmit the media content along with informationidentifying that at least one of the authorized recipients associatedtherewith from the client device to a network accessible mediarepository for storage therein.
 12. The client device of claim 11,wherein the processor is configured to provide at least one prompt to auser of the client device and to receive a user selection of the atleast one of the authorized recipients responsive to the at least oneprompt.
 13. The client device of claim 12, wherein the processor isconfigured to associate the at least one of the authorized recipientswith the media content and to transmit the media content along withinformation identifying that at least one of the authorized recipientsassociated therewith from the client device to the network accessiblemedia repository responsive to the at least one prompt.
 14. The clientdevice of claim 12, wherein the client device further comprises adisplay that is communicatively coupled to the processor and the atleast one prompt is a visual prompt on the display.
 15. The clientdevice of claim 12, wherein the client device further comprises aspeaker that is communicatively coupled to the processor and the atleast one prompt is an audible prompt played through the speaker. 16.The client device of claim 11, wherein the media content record functionis configured to record the media content while the client devicemaintains a call session.
 17. The client device of claim 11, furthercomprising a soft record key that is communicatively coupled to themedia content record function, the media content record function beingconfigured to record the media content responsive to user invocation ofthe soft record key.
 18. The client device of claim 11, furthercomprising a hard record key that is communicatively coupled to themedia content record function, the media content record function beingconfigured to record the media content responsive to user invocation ofthe hard record key.
 19. The client device of claim 11, wherein themedia content is audio content.
 20. The client device of claim 11,wherein the client device is an Internet Protocol (IP) device.